The Job-File Workflow

A federation is often driven entirely from version-controlled AutoMap job files, with one shared design project and one .waj per parcel:

• Create a hollow ePublisher Designer project (a .wep file) to carry the shared design: no source document groups, no Generate Groups override, and no output destination selected in the project itself.

• Give each parcel a .waj that references the design project with useAsStationery="True", so that the project is used as Stationery rather than built. (A project used as Stationery does not bundle its format files, so ePublisher Designer must be installed on the machine that runs the parcel jobs.) Each parcel job carries its own <Files> manifest of source documents and routes deployment through the job's destination attribute with deployScope="groups".

• Give the shell a .waj that references the same design project the same way, with no <Files> element at all, and deployScope="shell".

Each parcel job stages a fresh project from the design project, injects its documents, builds a complete standalone site, and deploys only its content slice. The composition job then assembles the site. For more information about using a project as Stationery, see Using an ePublisher Project as Stationery.